Proper handling of length defined data fields in FIX messages #625
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… across a FIX data field that has a defined length given by a previous tag. - Added a unit test to DataDictionaryTests to verify that a message is read correctly
|
|
|
This pull request is intended to directly address the handling of the XML non-FIX payload message defined by the CME. This issue was addressed in the C++ version of QuickFIX in the extractField method of the message class as well. |
|
This fix can be linked to issue #301 as a solution |
|
I'm closing this, per previous comment. If I'm mistaken, please let me know. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
read correctly